Toll Payment Equipment

ABSTRACT

Methods, computer-readable media, software, and apparatuses provide a system for making toll payments using toll payment equipment. The system may include a mobile computing device, a toll gateway, and an insurance company computing device. The mobile computing device (e.g., a phone) may be configured to communicate with the toll gateway when a vehicle carrying the mobile computing device passes through the toll gateway. The mobile computing may send a signal to the insurance company computing device to cause the insurance company computing device to pay an appropriate toll or discounted toll (if applicable). The insurance company may maintain an account for a customer from which toll payments are made. In addition, the insurance company computing device may collect information about the vehicle as it passes through the toll gateway. The insurance company computing device may use this information to determine an insurance-related value, such as an insurance premium.

FIELD OF ART

Aspects of the disclosure generally relate to methods and computersystems, including one or more computers particularly configured and/orexecuting computer software. More particularly, aspects of thisdisclosure relate to a system for exchanging communications between aphone and toll gateway to collect information and toll payments.

BACKGROUND

Some roads (or highways, bridges, tunnels, etc.) require payments fortheir use. Such roads are commonly referred to as “toll roads” or“turnpikes” and such payments are commonly referred to as a “toll.” Themoney accrued from collecting toll payments may be used to maintain theroad for which the toll was collected. The toll charged may be based onan amount of distance a vehicle travels on the road, the time of daythat a vehicle travels on the road, and the type of vehicle that istraveling on the road (e.g., vehicles with different numbers of axelsmay be required to pay different tolls). If payment is not made when avehicle passes a toll, a driver or the vehicle's owner may be issued aticket or citation for using the road without paying the toll. The feeassociated with such ticket may often be for more than the toll paymentthat was due.

Historically, people have been employed to collect tolls at certainpoints along a road. For example, a person may be stationed in a tollbooth at the entrance or exit of a highway to collect the toll paymentas a vehicle enters or exits the highway, respectively. Getting throughsuch checkpoints may be frustrating for drivers. For example, driversmay be frustrated with the lines or traffic that may be formed as aresult of the time it takes to make toll payments. Drivers may alsobecome frustrated if they do not have the exact change or enough moneyon hand to pay for the toll.

To address some of these frustrations, more recently technology has beendeveloped to improve the toll payment process. Some companies ororganizations (e.g., EZ Pass) offer a service that allows toll paymentsto be collected automatically so that the vehicles do not have to stopand/or drivers do not need to pay cash for the toll. A company mayprovide a customer with a transponder that may be placed in thecustomer's vehicle so that when the vehicle is driven through a tollgateway the transponder is detected. Detection of the transponder maycause an account to be automatically charged for the toll.

This more recent toll payment process may be considered an improvementover the traditional collection process, but is not withoutdisadvantages as well. In some cases, customers may have to pay a fee toacquire the transponder. Also, customers may be charged if they lose thetransponder. Further, a customer may have multiple vehicles and may needa transponder in each of their vehicles or may have to remember to movethe transponder into their different vehicles. In some cases, customershave been known to forget to put their transponder in their vehicle.Also, customers may not have their transponder with them when they aredriving another vehicle, such as a friend's vehicle, a rental car, etc.Moreover, the customer may have to place the transponder on thewindshield or at another inconvenient/distracting spot on the vehicle.In some cases the transponder may not work if it is in, for example, aglove compartment of a vehicle.

In addition, customers may have to set up the account from which tollpayments are deducted. In some cases, this account may be linked with acustomer's bank account so that it is replenished at certain points.Alternatively, a customer may be responsible for manually managing theaccount and ensuring that the account has enough money in it when thecustomer's vehicle goes through a toll checkpoint. If the customer failsto have enough money in the account, the customer may receive a ticketor be charged a surcharge fee (or another extra fee).

In light of the above, despite advancements in technology, there arestill challenges and disadvantages with respect to the toll paymentprocess. Accordingly, new systems, devices, methodologies, and softwareare desired to facilitate toll payments.

BRIEF SUMMARY

In light of the foregoing background, the following presents asimplified summary of the present disclosure in order to provide a basicunderstanding of some aspects of the invention. This summary is not anextensive overview of the invention. It is not intended to identify keyor critical elements of the invention or to delineate the scope of theinvention. The following summary merely presents some concepts of theinvention in a simplified form as a prelude to the more detaileddescription provided below.

Aspects of the disclosure address one or more of the issues mentionedabove by disclosing methods, computer readable storage media, software,systems, and apparatuses for making a toll payment using toll paymentequipment, such as a cellular phone. A phone travelling in a vehicle maycommunicate with a toll gateway and a computing device at an insurancecompany to pay the toll due for driving the vehicle through the tollgateway. The phone may send a signal to an insurance company computingdevice to cause the insurance company computing device to pay anappropriate toll. In some cases, the insurance company may give acustomer a discount on the toll. The insurance company may maintain anaccount for a customer from which toll payments are made. In addition,the insurance company may collect information about the vehicle as itpasses through the toll gateway. The insurance company may use thisinformation to determine an insurance-related value, such as aninsurance premium.

Aspects of this disclosure provide a system including a first computingdevice associated with a first vehicle, wherein the first computingdevice is configured to send and receive cellular phone calls. Thesystem may also include a toll gateway configured to detect the firstvehicle if the first vehicle passes through the toll gateway andcommunicate with the first computing device. The system may furtherinclude an insurance company computing device (which may be a computingdevice owned or maintained by or for an insurance company) configured totransfer funds from an account associated with the first computingdevice in response to receiving, from the first computing device or thetoll gateway, a signal indicating that the first vehicle passed throughthe toll gateway. The insurance company computing device may also beconfigured to receive, from the first computing device or the tollgateway, drive data of the first vehicle while the first vehicle passedthrough the toll gateway and to determine an insurance related valuebased on the drive data.

Aspects of the disclosure also provide the computing devices of thesystem as well as the computer readable media of those computing devicesthat store one or more toll equipment programs. Specifically, aspects ofthe disclosure provide a computing device, including a network interfaceconfigured to communicate, via a network, with a mobile computing deviceand a toll gateway, wherein the mobile computing device is configuredfor use in cellular phone calls and wherein the toll gateway isconfigured to detect a vehicle if the vehicle passes through the tollgateway. The computing device may also include at least one processorconfigured to execute computer-executable instructions stored oncomputer readable media. The at least one processor may be configured toreceive, from the mobile computing device or the toll gateway via thenetwork interface, a signal indicating that the vehicle passed throughthe toll gateway. The at least one processor may also be configured to,in response to receiving the signal, transmit an electronic payment fora toll associated with the toll gateway. Further, the at least oneprocessor may be configured to receive drive data of the vehicle whilethe vehicle passed through the toll gateway, and determine an insurancerelated value (e.g., an insurance premium, an insurance deductible, or adrive score used in determining the insurance premium or the insurancedeductible) based on the drive data. In some examples, the processor mayaccess, read, and write data to a particular memory device. The memorydevice may store computer-executable instructions of one or more tollequipment programs.

Aspects of the disclosure further provide a method of making tollpayments using a mobile computing device (e.g., a phone). The method mayinclude receiving, by a mobile computing device configured for use incellular phone calls, a beacon signal as the mobile computing devicewithin a vehicle passes through a toll gateway; transmitting, to aninsurance company computing device via a cellular backhaul, a signalindicating that the vehicle has passed through the toll gateway; inresponse to receiving the signal, determining an account associated withthe mobile computing device; transferring funds from the account to paya toll associated with the toll gateway; receiving, from the mobilecomputing device or the toll gateway, drive data of the vehicle whilethe vehicle passed through the toll gateway; and determining aninsurance related value based on the drive data.

Of course, the methods, devices, and systems of the above-referencedembodiments may also include other additional elements, steps,computer-executable instructions, or computer-readable data structures.In this regard, other embodiments are disclosed and claimed herein aswell. The details of these and other embodiments of the presentinvention are set forth in the accompanying drawings and the descriptionbelow. Other features and advantages of the invention will be apparentfrom the description, drawings, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and is notlimited by the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 is a block diagram of an example computing device that may beused according to an illustrative embodiment of the present disclosure.

FIG. 2 illustrates an example network environment in which a system inaccordance with the present disclosure may be implemented.

FIGS. 3-6 illustrate flow diagrams of example processes in accordancewith aspects of the present disclosure.

FIG. 7 illustrates a diagram of an example sequence of signals inaccordance with aspects of the present disclosure

FIG. 8 illustrates a diagram of an example interface presented bycomputing devices configured according to aspects of the presentdisclosure.

DETAILED DESCRIPTION

In accordance with various aspects of the disclosure, methods,computer-readable media, software, and apparatuses are disclosed thatprovide a system for making toll payments using toll payment equipment,such as a phone. The toll payment system may allow users to use theircell phones to pay tolls. A user may drive through a toll gatewaywithout stopping and her phone may communicate with the toll gateway tosatisfy payment of the toll. The toll gateway and/or phone maycommunicate with a backend system that may transfer the funds for thetoll. Information captured as the user passes through the toll gatewaymay be used to provide discounts on the toll or other insurance relatedpayments (e.g., insurance premiums or insurance deductibles).

The toll payment system may include a cell phone (traveling in avehicle) that assists in paying a toll when a car passes through a tollgateway. The toll gateway may send a signal to the cell phone when thecell phone is in proximity to the toll gateway. The cell phone mayreceive the signal and send another signal to a computer or server thatautomatically transfers the dollar amount of the toll from apre-established toll account to the toll company. The cell phone mayalso send a response signal to the toll gateway indicating that thesignal from the gateway was received and/or that the pre-establishedtoll account is operating properly (e.g., that the toll payment has beenmade or will be made). If the toll gateway does not receive the properreturn signal from the cell phone, the toll gateway may use a camera totake one or more photographs of the vehicle. In particular, the cameramay be operated to take a photograph of the license plate of the vehiclefor future processing and issuance of a ticket. The cell phone mayfurther provide an indication, such as an audible tone, that can beheard by the driver of the car when the toll payment is completed (e.g.,when the response signal is sent to the toll gateway).

Further, information may be sent to an insurance company regardingpayment of the toll. This information may include the time and locationof the payment, the speed of the phone during the payment, and/or theproximity of the phone to other phones at the time of payment. In someembodiments, an insurance company may use this information as ratingfactors in setting insurance premiums for the customer. The insurancecompany may provide the customer with a discount on the toll payment inexchange for allowing use of the customer data or in exchange for thecustomer receiving audio or visual advertisements after the tollpayment. The insurance company may also manage the pre-established tollaccount in some examples.

The toll payment system may allow for situations where several cellphones are in the same car. In such a situation, the phones maycommunicate with each other and determine which of the phones is thedominant phone responsible for communicating with the toll gateway.After this determination, only the dominant phone may communicate withthe toll gateway. The determination of the dominant phone can be basedon preferences set by the users of the phones or based on the locationof the phones within the vehicle. The relation of the phones within thevehicle may be determined by determining the location of the phones inrelation to an on-board diagnostic port (e.g., the OBD II port) of thevehicle.

In the following description of the various embodiments of thedisclosure, reference is made to the accompanying drawings, which form apart hereof, and in which is shown by way of illustration, variousembodiments in which the disclosure may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made.

In one or more arrangements, teachings of the present disclosure may beimplemented with a computing device. FIG. 1 illustrates a block diagramof an example computing device 100 that may be used according to anillustrative embodiment of the present disclosure. The computing device100 may be similar to any available computing device, such as a personalcomputer (e.g., a desktop computer), server, laptop computer, notebook,tablet, smartphone, etc. The computing device 100 may have a tollinformation manager 101 for performing methods and executinginstructions of the one or more toll equipment programs describedherein. The toll information manager 101 may be implemented with one ormore processors and one or more storage units (e.g., databases, RAM,ROM, and other computer-readable media), one or more applicationspecific integrated circuits (ASICs), and/or other hardware components.Throughout this disclosure, the toll information manager 101 may referto the software and/or hardware used to implement the toll informationmanager 101. The one or more processors of the toll information manager101 may operate in addition to or in conjunction with another generalprocessor 103 of the computing device 100. Both the toll informationmanager 101 and the processor 103 may be capable of controllingoperations of the computing device 100 and its associated components,including RAM 105, ROM 107, an input/output (I/O) module 109, a networkinterface 111, and memory 113.

The I/O module 109 may be configured to connect to an input device 115,such as a microphone, keypad, keyboard, touchscreen, and/or stylusthrough which a user of the computing device 100 may provide input data.The I/O module 109 may also be configured to connect to a display device117, such as a monitor, television, touchscreen, etc., and may include agraphics card. The display device 117 and input device 115 are shown asseparate elements from the computing device 100, however, they may bewithin the same structure. Using the input device 115, systemadministrators may update various aspects of the toll equipmentprogram(s), such as rules for making toll payments, rules for collectinginformation, rules for handling communications between toll gateways,phones, and backend computing devices. On some computing devices 100,the input device 115 may be operated by users (e.g., customers) tointeract with the toll equipment program, including providing userinformation and/or preferences, providing vehicle information (e.g.,make and model of a vehicle), reviewing toll payments, viewingadvertisements, reviewing driving behavior data, etc., as describedherein. Meanwhile, the display device 117 may assist the systemadministrators and users to confirm/appreciate their inputs.

The memory 113 may be any computer readable medium for storing computerexecutable instructions (e.g., software). The instructions stored withinmemory 113 may enable the computing device 100 to perform variousfunctions. For example, memory 113 may store software used by thecomputing device 100, such as an operating system 119 and applicationprograms 121, and may include an associated database 123.

The network interface 111 allows the computing device 100 to connect toand communicate with a network 130. The network 130 may be any type ofnetwork, including a local area network (LAN) and/or a wide area network(WAN), such as the Internet, a cellular network, or satellite network.Through the network 130, the computing device 100 may communicate withone or more other computing devices 140, such as laptops, notebooks,smartphones, personal computers, servers, etc. The computing devices 140may also be configured in a similar manner as computing device 100. Insome embodiments the computing device 100 may be connected to thecomputing devices 140 to form a “cloud” computing environment.

The network interface 111 may connect to the network 130 viacommunication lines, such as coaxial cable, fiber optic cable, etc. orwirelessly using a cellular backhaul or a wireless standard, such asIEEE 802.11, IEEE 802.15, IEEE 802.16, etc. In some embodiments, thenetwork interface may include a modem. Further, the network interface111 may use various protocols, including TCP/IP, Ethernet, File TransferProtocol (FTP), Hypertext Transfer Protocol (HTTP), etc., to communicatewith other computing devices 140.

FIG. 1 is an example embodiment of a computing device 100. In otherembodiments, the computing device 100 may include fewer or moreelements. For example, the computing device 100 might not include theprocessor 103 in addition to one or more processors of the tollinformation manager 101. On the other hand, the computing device 100 maybe a mobile device (e.g., a smartphone, tablet, etc.), and thus, mayalso include various other components, such as a battery, speaker,and/or antennas (not shown). Also, the computing device 100 may be avehicle computing device 100 (either installed by a vehicle manufactureror as an aftermarket part) having vehicle compatible elements, such as aport for an on-board diagnostic connector or ports for other vehiclesensors (e.g., tire pressure sensors, engine temperature sensors,speedometer, odometer, etc.).

The methods and software for facilitating toll payments as disclosedherein may be implemented on one or more computing devices 100 used invarious network environments. FIG. 2 illustrates an example networkenvironment 200 for implementing methods according to the presentdisclosure. As shown in FIG. 2, the network environment 200 may includea network 201 configured to connect computing devices within orassociated with one or more vehicles 202, computing devices of the tollgateway 203, one or more toll management computing devices 204, and oneor more insurance company computing devices 205. Collectively, thesecomputing devices may form a toll payment system. The network 201 may beany type of network, like the network 130 described above, and use oneor more communication protocols (e.g., protocols for the Internet (IP),Bluetooth, cellular communications, satellite communications, etc.) toconnect computing devices and servers within the network environment 200so they may send and receive communications between each other. Inparticular, the network 201 may include a cellular network and itscomponents, such as cell towers 206. Accordingly, for example, a mobilecomputing device 100 m (e.g., a smartphone) of a person in vehicle 202may communicate, via a cell tower 206 of a cellular backhaul of thenetwork 201, with an insurance company computing device 205 to cause theinsurance company computing device 205 to transfer an electronic paymentto the toll management computing device 204. While FIG. 2 illustratesthat the mobile computing devices 100 m are within the vehicle 202, itshould be understood that these same mobile computing devices 100 m mayconnect to the network 201 even if they are removed from the vehicle202.

FIG. 2 illustrates only one vehicle 302. However, the toll paymentsystem may be configured to send and receive communications withmultiple vehicles 202 simultaneously so that it may process multipletoll payments simultaneously. Also, although FIG. 2 depicts the vehicle202 as a car, the vehicle 202 may be any type of vehicle, including amotorcycle, bicycle, scooter, drone (or other automated device), truck,bus, boat, plane, helicopter, etc.

Similarly, although FIG. 2 only shows one toll gateway, it should beunderstood that the toll payment system may include multiple tollgateways 203 at the same location (e.g., same entrance or exit to a tollroad) and/or multiple toll gateways at different locations. Further, thetoll payment system may be configured to send and receive communicationswith multiple toll gateways 203 simultaneously.

FIG. 2 also illustrates an example subsystem within the networkenvironment 200. Specifically, FIG. 2 illustrates an example arrangementof computing devices that may exist within a vehicle 202. As shown inthe example of FIG. 2, the vehicle 202 may include two mobile computingdevices 100 m, a vehicle computing device 100 v, and an on boarddiagnostic connector (OBD II). One mobile computing device 100 m may bea smartphone of one person (e.g., a driver), and the other mobilecomputing device 100 m may be a smartphone of another person (e.g., apassenger). In some embodiments, the mobile computing devices 100 m maycommunicate with each other (e.g., via Bluetooth) to determine whichmobile computing device will be responsible for assisting in making tollpayments. Moreover, one or more of the mobile computing devices 100 mmay communicate (e.g., via Bluetooth) with the vehicle computing device100 v and/or a device connected to the vehicle's OBD II connector 207.Although FIG. 2 depicts the mobile computing devices 100 m assmartphones, the mobile computing devices 100 m may be any mobilecomputing device (e.g., a tablet, personal digital assistant (PDA),smart-watch, satellite phone, etc.). The mobile computing devices 100 mmay be associated with a driver or passenger of the vehicle 202. Themobile computing device 100 m may be configured in a similar manner tothe computing device 100 of FIG. 1. Further, the mobile computing device100 m may be configured to execute a client-side toll equipment programthat handles communications with toll gateways and backend systemcomputing devices, such as the toll management computing device 204 orinsurance company computing device 205 and provides a user interface fora client to provide inputs to and receive outputs from the toll paymentsystem. Such a client-side toll equipment program may be downloaded orotherwise installed onto the mobile computing devices 100 m using knownmethods. Once installed onto the vehicle computing device 100 v, a usermay launch the client-side toll equipment program by, for example,operating buttons or a touchscreen on the mobile computing device 100 m.Additionally, or alternatively, the mobile computing device 100 m may beconfigured to execute a web browser (e.g., an application for accessingand navigating the Internet) to access a web page providing an interfacefor the toll payment system. In some embodiments, the mobile computingdevice 100 m may also be configured to collect drive data using, e.g.,its accelerometer, GPS, gyroscope, etc. Drive data may include vehicletelematics data or any other data related to events occurring during avehicle's trip (e.g., an impact to a part of the vehicle, a deployedairbag, etc.). Drive data may also include location information, such asGPS coordinates, indicating the geographical location of the mobilecomputing devices 100 m.

Although FIG. 2 depicts two mobile computing devices 100 m within thevehicle 202, there may be more or less mobile computing devices 100 m insome cases. For example, the vehicle 202 may carry additionalpassengers, and each person may have one or more mobile computingdevices 100 m. Or, for example, the people in the customer vehicle 302might not have a mobile computing device 100 m or might have left theirmobile computing device 100 m elsewhere. Also, if the vehicle isautonomous, there might not be any mobile computing device 100 m.

As mentioned above, the vehicle 202 may also include a vehicle computingdevice 100 v. The vehicle computing device 100 v may be configured in asimilar manner to the computing device 100 of FIG. 1. Further, thevehicle computing device 100 v may be configured to execute theclient-side toll equipment program that provides a user interface for acustomer to provide inputs to and receive outputs from the toll paymentsystem. Such a client-side toll equipment program may be downloaded orotherwise installed onto the vehicle computing device 100 v using knownmethods. Once installed onto the vehicle computing device 100 v, a usermay launch the client-side toll equipment program by, for example,operating buttons or a touchscreen on the dashboard of the vehicle 202.In some examples, the client-side toll equipment program may beautomatically launched whenever the vehicle 202 is started or put ingear. Additionally, or alternatively, the vehicle computing device 100 vmay be configured to execute a web browser to access a web pageproviding an interface for the toll payment system. In some embodiments,the vehicle computing device 100 v may also be configured to collectdrive data using, e.g., its accelerometer, GPS, gyroscope, etc. Asmentioned above, this drive data may include vehicle telematics data orany other data related to events occurring during a vehicle's trip(e.g., an impact to a part of the vehicle, a deployed airbag, or otherevent triggered by a sensor of the vehicle). The vehicle 202 may have aGPS installed therein, and therefore, the vehicle computing device 100 vmay also collect GPS coordinates.

As mentioned above, the vehicle computing device 100 v and/or mobilecomputing devices 100 m may communicate with the vehicle's on-boarddiagnostic (OBD) system 207, which is typically located beneath thesteering wheel of the vehicle 202. In some embodiments, a device may beconnected to the OBD II connector of the vehicle 202 to assist in makingtoll payments. In such an embodiment, the device connected to the OBD IIconnector may be used instead of a mobile computing device 100 m (e.g.,a phone). In some embodiments, the OBD system 207 may be used inconjunction with mobile computing devices 100 m to obtain data (e.g.,from vehicle sensors such as a fuel gauge, tire pressure sensors, enginetemperature sensors, etc.) about the vehicle at the time of passingthrough a toll gateway. Also, in some examples, the OBD system mayassist multiple mobile computing devices 100 m within the same vehicle202 in determining which mobile computing device is dominant, andtherefore, responsible for making the toll payment.

In some embodiments, one or more vehicles 202 may be autonomous or in anautonomous mode (e.g., auto-pilot mode). An autonomously controlledvehicle 202 may be controlled by its vehicle computing device 100 vand/or a remote computing device. The vehicle computing device 100 v mayemploy sensors for inputting information related to the vehicle'ssurroundings (e.g., distance from nearby objects) and use the inputtedinformation to control components of the vehicle 202 to steer andaccelerate/decelerate the vehicle 202.

FIG. 2 also illustrates another subsystem referred to herein as the tollgateway 203. The toll gateway may be configured to detect one or morevehicles 202 as they pass through the toll gateway 203. As shown in FIG.2, the toll gateway 203 may include a toll booth 208, a toll gatewaycomputing device 209, one or more toll gateway transceivers 210, and acamera. The toll gateway may include additional infrastructure anddevices, such as sensors, to detect when vehicles 202 pass through thetoll gateway. Although only one toll gateway is shown, it should beunderstood that a number of toll gateways 203 may be located at the samecheckpoint (e.g., entrance to a highway). Also, other toll gateways 203may be located at other locations, but may still communicate with thetoll management computing device 204 and insurance company computingdevice 205.

Some people might not have a means for automatically making a tollpayment (e.g., might not have a smartphone with the client-side tollequipment program installed thereon), and therefore, may have to pay thetoll in cash to an attendant working in the toll booth 208 or drop moneyinto a basket on the toll booth 208. However, if the mobile computingdevice 100 m in the vehicle 202 is running the client-side tollequipment program, the vehicle 202 does not have to stop at the tollbooth 208 to make the toll payment. Instead, the vehicle 202 maycontinue moving and the mobile computing device 100 m (or another devicein the vehicle such as the vehicle computing device 100 v) maycommunicate with the toll gateway computing device 209 and/or tollgateway transceivers 210 as the vehicle 202 moves through the tollgateway 203. The toll gateway computing device 209 may communicate withthe toll management computing device 204 or insurance company computingdevice 205 via the network 201. For example, the toll gateway computingdevice 209 may communicate with the toll management computing device 204to confirm that the toll payment was successfully received.

The toll gateway transceivers 210 may transmit a beacon signal that maybe detected by any mobile computing device 100 m passing through thetoll. FIG. 2 shows three toll gateway transceivers 210 for a single tollgateway 203; however, fewer or more toll gateway transceivers 210 may beused for a single toll gateway 203. More than one toll gatewaytransceiver 210 may be used for each toll gateway 203 in order toimprove the coverage area of the beacon signal and ensure that thebeacon signal is picked up by any mobile computing device 100 m passingthrough the toll gateway 203. In some embodiments, where multiple tollgateway transceivers 210 are used for a single toll gateway 203, themultiple toll gateway transceivers 210 may transmit beacons signals withthe same frequency and/or information. Alternatively, in someembodiments, the multiple toll gateway transceivers 210 may eachtransmit a beacon signal with a different frequency and/or differentinformation. Further, the beacon signals may be transmitted continuouslyor intermittently (e.g., periodically). Where there are multiple tollgateway transceivers 210 for a single toll gateway 203, the toll gatewaytransceivers 210 may transmit the beacon signals at the same time or atdifferent times (e.g., at offset intervals).

The beacon signal transmitted by the toll gateway transceivers 210 maybe any radio frequency (RF) signal. Further, the beacon signal mayinclude a variety of information, such as an identifier that identifiesthe toll gateway 203. The identifier may be unique to the toll gateway203 at that checkpoint or unique to the toll gateway 203 with respect toall toll gateways 203 in the system. The toll gateway transceivers 210may be programmable so that the information included in the beaconsignals may be updated. In addition to transmitting beacon signals, thetoll gateway transceivers 210 may be configured to receive responsesfrom mobile computing devices 100 m. For example, the toll gatewaytransceivers 210 may be configured to receive an RF signal indicatingthat a mobile computing device 100 m received the signal from the tollgateway transceivers 210 and/or indicating that the toll payment wasmade.

The toll gateway transceivers 210 may also communicate with the tollgateway computing device 209. A communication from the toll gatewaytransceivers 210 to the toll gateway computing device 209 may inform thetoll gateway computing device 209 when a mobile computing device 100 mis detected. Further, the toll gateway transceiver 210 may provideinformation to the toll gateway computing device 209 related to adriving behavior (e.g., speed) of a vehicle 202 as the vehicle 202passes through the toll gateway 203. Such speed may be determined bydetermining the speed of a mobile computing device 100 m within thevehicle 202 and assuming the speed of the mobile computing device 100 mrepresents the speed of the vehicle 202. Moreover, in some embodiments,a toll gateway transceiver 209 may inform the toll gateway computingdevice 210 that a mobile computing device 100 m passed through the toll,but did not pay the fees.

In such cases where the toll payment is not made, the toll gatewaycomputing device 210 may automatically operate the camera 211. Forexample, the toll gateway computing device may cause the camera to takea photograph if a vehicle passes a toll gateway 203 and does not pay thetoll and/or there are not enough funds in an account associated with thevehicle to cover the toll. In some embodiments, the camera 211 may takebe pre-set to take a photograph of every vehicle that passes through thetoll gateway 203, and the toll gateway computing device may determinewhich photographs to store and which ones to delete. For example, thetoll gateway computing device 209 may determine to flag a photograph ofa particular vehicle that did not pay and store the vehicle inassociation with information indicating non-payment for later processingof a ticket or citation.

The camera 211 may be any type of camera and may be able to capturevideo, audio, and/or still photographs. In some embodiments, the camera211 may have a fixed orientation, while in other embodiments, thecamera's orientation may be controlled by the toll computing device 209or another device. For example, the toll computing device 209 maycontrol the orientation of the camera 211 to take a photograph of alicense plate of a vehicle 202. The toll computing device 209 mayinclude software (e.g., pattern recognition software) for discerning thelicense plate number from the photograph. Then, the toll computingdevice 209 may store the license plate number identified from thephotograph with the image data (e.g., pixel information) for thephotograph and other information, such as information indicating thatthe toll was not paid for the vehicle 202. The camera 211 may also beused to capture other information, such as tailgating information. Forexample, the camera 211 may take a video or photographs of consecutivevehicles 202 passing through a toll gateway 203 and the toll gatewaycomputing device 209 may use the captured video or photographs todetermine whether the second vehicle 202 is tailgating the first vehicle202. For example, the toll gateway computing device 209 may analyze avideo to determine a distance and/or time between two vehicles todetermine whether the second vehicle is tailgating the first vehicle.Such tailgating information may be of interest to an insurance companyseeking to determine the driving behaviors of their customers for thepurpose of determining risk and calculating insurance relatedinformation (e.g., insurance premiums, insurance deductibles, etc.). Forexample, a driver who tailgates another driver through a toll gateway203 may be deemed to be a riskier driver than a driver who does nottailgate, and therefore, may be a bigger liability to an insurancecompany than the driver who does not tailgate. In some embodiments, aninsurance company may use the tailgating information obtained from thecamera 211 at the toll gateway 203 to reward drivers for not tailgatingto warn drivers who do tailgate.

FIG. 2 also shows toll management computing devices 204, which maybelong to a toll company operating the toll gateway 203. The tollcompany may be a private or public company or government operatedentity. The toll management computing devices 204 may be configuredsimilar to the computing device 100 of FIG. 1. The toll managementcomputing devices 204 may be configured to store records or logsindicating which vehicles passed through the toll gateway 203. The tollmanagement computing devices 204 may also be configured to process moneytransfers for toll payments. For example, the toll management computingdevices 204 may receive an electronic payment for a toll from theinsurance company computing devices 205 and update a driver or vehicleaccount for which the toll was paid. If a toll is not paid, the tollmanagement computing devices 204 may issue tickets or citations (whichmay include generating ticket numbers and determining a dollar amount ofthe fine). Further, the toll management computing devices 204 may alsohandle billing matters and/or generate reports. For example, the tollmanagement computing devices 204 may generate a monthly bill or reportfor a customer that indicates the tolls owed by the customer for themonth. Such a bill may be itemized to inform the customer each timetheir vehicle passed through a toll gateway and how much was charged.The toll management computing devices 204 may deliver such bills andreports to the appropriate customer via email or other electronic formsof communication.

In addition, FIG. 2 depicts insurance company computing devices 205. Theinsurance company computing devices 205 may belong to an insurancecompany that provides insurance (e.g., automotive insurance), or toanother company that manages and maintains the insurance companycomputing devices 205 on behalf of (or for providing a service to) aninsurance company. The insurance company computing devices 205 may beconfigured similar to the computing device 100 of FIG. 1. The insurancecompany computing devices 205 may be specially configured (e.g.,programmed) to communicate with mobile computing devices 100 m. Inparticular, the insurance company computing devices 205 may beconfigured to receive indications from mobile computing devices 100 mwhen they pass through toll gateways 203. Based on the informationreceived, the insurance company computing devices 205 may determinewhich toll company should be paid and a dollar amount that should betransferred to the toll company. The insurance company computing devices205 may manage accounts for their customers from which money is deductedto pay tolls. The accounts may be set up on a per vehicle basis, perdriver basis, or per insurance policy basis. For example, a husband andwife may be on the same insurance policy and have one account for payingtolls whenever either one of them pass through a toll gateway 203.

The insurance company computing devices 205 may also transmitinformation to the mobile computing devices 100 m regarding tollpayments and other driving behavior information (e.g., informationindicating that the driver is speeding through the toll gateway ortailgating). The insurance company computing devices 205 may communicatewith the toll gateway computing device 209 or toll management computingdevices 204 to receive driving behavior information for their customerswhile their customers passed through a toll gateway 203. For example,the insurance company computing devices 205 may receive driving behaviorinformation from a toll gateway computing device 209 indicating that adriver insured by the insurance company was tailgating or speeding asthey passed through the toll gateway 203.

In some embodiments, the insurance company computing devices 205 maydetermine insurance related information (e.g., insurance premiums,insurance deductibles, etc.) based on driving behavior informationobtained. Additionally, or alternatively, the insurance companycomputing devices 205 may determine discounts to be applied. Discountsmay be earned for simply passing through the toll gateway 203 or fordriving well (e.g., not speeding) through the toll gateway 203. Theinsurance company computing devices 205 may also determine when, howmany, and/or which advertisements are to be sent to a customer afterthey pass through a toll gateway 203. In some embodiments, a customermay avoid paying for a toll with money in exchange for receiving and/orviewing advertisements.

Although the insurance company computing devices 205 are shown asseparate from the toll management computing devices 204 in FIG. 2, insome embodiments the insurance company may manage the toll gateways 203and therefore the insurance company computing devices 205 may be thesame as (or merged with or located in the same place as) the tollmanagement computing devices 204. It should also be understood, that theinsurance company computing devices 205 may include various computingdevices used by an insurance company for various insurance relatedservices. For example, the insurance company computing devices 205 mayinclude computing devices for tracking insurance claims, managinginsurance policy information, etc. In some embodiments, one or more ofthe insurance company computing devices 205 may be configured to host awebsite for the insurance company through which customers may view andupdate information on their insurance (e.g., automotive insurance)policy.

FIG. 3 illustrates a flow diagram for an example method in accordancewith aspects of the present disclosure. More specifically, FIG. 3illustrates a plurality of steps of a method for making a toll payment.The steps of FIG. 3 may be performed by various devices disclosedherein, and in particular a mobile computing device 100 m, such as acell phone of a driver or passenger of the vehicle 202. One or more ofthe steps of FIG. 3 may be performed by executing a client-side tollequipment program and/or operating a particularly configured computingdevice 100 of the toll payment system. As a result of the method of FIG.3, a person may use his/her phone (e.g., cell phone) to pay a toll.

The method of FIG. 3 may begin with a step 301 of configuring and/orregistering the computing devices of the toll payment system. Forexample, configuring a mobile computing device 100 m of a customer of aninsurance company may include downloading and installing a tollequipment program. Different mobile computing devices 100 m may installdifferent versions of the toll equipment program depending on a platformof the mobile computing device 100 m. For example, a mobile computingdevice running the iOS™ operating system may download a differentversion of the toll equipment program than a device running the ANDROID™operating system.

In some embodiments, step 301 may also include registering a computingdevice with the organization operating/managing the toll gateway 203and/or an insurance company. Registering a computing device may includecreating and/or logging into an account with an associated usernameand/or password. The account may be associated with the mobile computingdevice 100 m and/or an insurance policy of a user of the mobilecomputing device 100 m. To perform registration, the organizationproviding the insurance company may request various information,including information regarding a user device (e.g., device identifier,device make, device model, etc.), information regarding a user (e.g.,name, birthdate, address, insurance policy number, etc.), and/orinformation regarding a vehicle (e.g., make, model, year, vehicleidentification number (VIN), etc.). Registration may also includesetting up an account for billing purposes. For example, registrationmay include establishing an account with the insurance company fromwhich toll payments are deducted. Establishing this account may includedepositing money into the account. Additionally, establishing thisaccount may include linking the account with a user's banking account(e.g., checking or savings account) so that funds may be replenishedautomatically to cover toll payments.

In some embodiments, when registering with the toll payment system, auser may create a profile. The profile may include certain userpreferences so that a customized experience may be realized. Forexample, a user may create settings that define whether they willreceive advertisements, which advertisements they will receive, whenthey will receive advertisements, and/or how many advertisements theywill receive. A user may also create settings that define which mobilecomputing device 100 m will be responsible for triggering toll paymentswhen multiple mobile computing devices 100 m are within a vehicle 202 atthe time of passing through the toll gateway 203.

In some embodiments, step 301 may also include performing a test. Forexample, the mobile computing device 100 m may send a test signal to theinsurance company computing devices 205 to trigger the insurance companycomputing devices 205 to make a toll payment. The insurance companycomputing devices 205 may then transfer a small amount (e.g., one cent)to the toll management computing devices 204. Next, the insurancecompany computing devices 205 or toll management computing devices 204may send a test result notification to the mobile computing device 100 mindicating whether the test was successful (e.g., whether toll paymentis working properly). This test may help to give users confidence thattheir phones will work properly to make toll payments and that they willnot receive a ticket for non-payment of a toll.

In step 303, the toll equipment program installed on the mobilecomputing device 100 m may be executed. Where the toll equipment programis an “app” on a smartphone, step 303 may include a user selecting the“app” and the operating system of the smartphone running the “app.” Thisclient-side toll equipment program may be continuously run in thebackground of the mobile computing device 100 m so that it is configuredto assist in making toll payments whenever a user happens to passthrough a toll gateway 203. In other words, the toll equipment programmay run in the background continuously so that users do not have tointeract with the program each time they are about to pass through atoll gateway 203. Because the client-side toll equipment program may runin the background it might not be distracting to users wishing toperform other operations with their mobile computing devices 100 m, andtherefore, users may be more likely to adopt the client-side tollequipment program. In some embodiments, once launched, the client-sidetoll equipment program may be launched automatically each time themobile computing device 100 m is powered on. Thus, if the mobilecomputing device 100 m is turned off or its battery dies, theclient-side toll equipment program may be automatically launched againwhen the mobile computing device 100 m is turned back on or powered backup.

In some embodiments, the client-side toll equipment program may enter asleep mode so as not to drain the battery of the mobile computing device100 m when it is unlikely to pass through a toll gateway. Whether theclient-side toll equipment program is in a sleep mode or not may bebased on acceleration data obtained from the accelerometer (orgyroscope) or GPS receiver of the mobile computing device 100 m. Forexample, if the client-side toll equipment program determines that itshost phone has not exceeded a certain speed in a while (e.g., has notexceeded 20 mph in the last 15 minutes), it may assume that it is not ina vehicle 202 and therefore not likely to pass through a toll gateway203.

At step 305, the mobile computing device 100 m (e.g., a cell phone,smartphone, etc.) may receive a signal from the toll gateway 203. Forexample, the mobile computing device 100 m may receive a beacon signaltransmitted by one or more of the toll gateway transceivers 210illustrated in FIG. 2. The beacon signal may include information, suchas an identifier of the toll gateway 203, an amount of a toll owed,and/or a time and/or date that the mobile computing device 100 m passedthrough the toll gateway 203. In some embodiments, the beacon signal mayalso include additional information. For example, this additionalinformation may include a speed of the vehicle 202 passing through thetoll gateway 203, which may be detected using radar equipment of thetoll gateway 203. Also, for example, the additional information mayinclude a tailgating distance, which may indicate a distance that thevehicle 202 passing through the gateway was from the previous vehiclethat passed through the toll gateway 203.

At step 307, the mobile computing device 100 m may determine whether it(and therefore a vehicle 202 carrying it) has passed through a tollgateway 203. The mobile computing device 100 m may analyze the signalreceived in step 305 to make this determination. The mobile computingdevice 100 m may receive various signals for various purposes, such aspush notifications for various apps running on the mobile computingdevice 100 m, cell signals for conducting phone calls with the mobilecomputing device 100 m, and text messages. The mobile computing device100 m may be configured to distinguish a beacon signal from a tollgateway 203 from these other types of signals to determine when themobile computing device 100 m passes through a toll gateway 203. Theclient-side toll equipment program executing on the mobile computingdevice 100 m may monitor all signals and determine which ones are beaconsignals from a toll gateway 203. If the mobile computing device 100 mdetermines, for example, that a received signal does not correspond to abeacon signal (No at step 307), the process may wait until the nextsignal is received at step 305 again.

If the mobile computing device 100 m determines that it has passedthrough a toll gateway at step 307 (Yes at step 307), the process mayadvance to step 309. In step 309, the mobile computing device 100 mdetermines whether a toll payment is required. In some embodiments,tolls may depend on a distance traveled. Therefore, there may be tollgateways 203 set up to determine when a vehicle first enters a tollroad. These toll gateways 203 might not charge a toll at the time ofentrance, but rather, may be used to detect where a vehicle has enteredthe toll road so that when the vehicle exits the toll road theappropriate amount owed based on the distance traveled can bedetermined. Accordingly, a toll might not be due each time a vehiclepasses through a toll gateway 203. Therefore, the mobile computingdevice 100 m may determine whether a toll payment is required at step309. This determination may be made using the toll equipment program. Insome embodiments, if a toll payment is not required, the mobilecomputing device 100 m may store information indicating that a tollgateway 203 has been passed so that when another toll gateway 203 ispassed, the mobile computing device 100 m may determine the distancetraveled and the appropriate amount owed or may send the information forthe two toll gateways 203 to the insurance company computing devices 205for determining the amount owed.

If a toll payment is required (Yes at step 309), the mobile computingdevice 100 m may transmit a signal to an insurance company computingdevice 205 (e.g., a server) at step 311. The signal may be a cell signalor other signal and may include information obtained from the tollgateway (e.g., an identifier of the toll gateway 203) and/or additionalinformation generated by the mobile computing device 100 m. Suchadditional information may include one or more identifiers (e.g., of themobile computing device 100 m, the user of the mobile computing device100 m, or the vehicle 202 carrying the mobile computing device 100 m), alocation of the mobile computing device (e.g., GPS coordinates), and atime that the mobile computing device 100 m passed through the tollgateway 203. Additionally, or alternatively, the additional informationmay include driving behavior information, such as a speed of the vehicleas it passes through the toll gateway 203 (which may be obtained fromthe vehicle computing device 100 v, the OBD device 207, the mobilecomputing device 100 m itself based on GPS coordinates or accelerometerdata).

In some cases, the mobile computing device 100 m sending the signal atstep 311 might not be the only mobile computing device 100 m within thevehicle 202. To prevent multiple mobile computing devices 100 m withinthe same vehicle 202 from sending a signal and causing multiple tollpayments to be made for a single vehicle 202, the mobile computingdevices 100 m within the same vehicle may communicate with one anotherto determine which one is responsible for transmitting the signal atstep 311. This determination of which mobile computing device is thedominant (or responsible) mobile computing device 100 m will be furtherdescribed below with respect to FIG. 6.

In step 313, the mobile computing device 100 m may send a signal back tothe toll gateway 203. For example, the mobile computing device 100 m maysend a response signal to the toll gateway transceivers 210 or tollgateway computing device 209. The signal sent at step 313 may be anytype of wireless signal sent using any protocol. For example, theresponse signal may be sent using the IEEE 802.11 protocol. A cellularsignal may also be used as the response signal at step 313; however, itis anticipated that the response signal will be sent while the vehicle202 is still in the vicinity of the toll gateway 203, and therefore, alocal wireless network connection between the mobile computing device100 m and toll gateway 203 may be possible.

The response signal transmitted at step 313 may include informationconfirming that the mobile computing device 100 m received the beaconsignal as it passed through the toll gateway 203. The response signalmay also indicate that the toll payment was made or will be made or thatthe toll payment system is otherwise working properly. In someembodiments, the response signal may also include additionalinformation, such as the speed of the vehicle 202, an identifier of thevehicle 202, an identifier of the mobile computing device 100 m,identifiers of other mobile computing devices 100 m within the vehicle202, etc.

In step 315, the mobile computing device 100 m may receive a response tothe signal it sent in step 311. The response may be received by themobile computing device 100 m from the toll management computing devices204 or insurance company device 205. The response may includeinformation indicating that the toll payment was successful. Forexample, the mobile computing device 100 m may receive a signal from theinsurance company computing device 205 indicating that the funds for thetoll were transferred to the toll management computing device 204. Or,for example, the mobile computing device 100 m may receive a signal fromthe insurance company computing device 205 indicating the toll paymentwas not made (e.g., because there were not enough funds in thecustomer's account with the insurance company).

In step 317, the mobile computing device 100 m may determine whether thefunds were transferred successfully. This determination may be madebased on the signal received at step 315.

If the mobile computing device 100 m determines that the funds were nottransferred successfully (No at step 317), the mobile computing device100 m may output a message indicating that the toll payment wasunsuccessful at step 319. Outputting this message may include playing anaudible tone (e.g., a beeping sound) or audible message (e.g., a voicerecording stating “the toll payment failed”). Additionally, oralternatively, the message may include text and/or an image displayed ona screen of the mobile computing device 100 m. Moreover, the message maybe communicated by causing the mobile computing device 100 m to vibrate.

In step 321, advertisements may be played (e.g., displayed) on themobile computing device 100 m. As a result of the failure to pay thetoll, the insurance company may cover the toll payment on behalf of thecustomer and provide the customer with advertisements to offset the costof covering the customer. The number or type of advertisements displayedmay depend on the customer, the amount of the toll that was due orunderpaid, how many tolls the customer has failed to pay in the past,etc.

In some embodiments, the advertisements may be presented automaticallyshortly after being received. In other embodiments, the advertisementsmay be stored locally by the mobile computing device 100 m for laterpresentation to the user (e.g., after the user finishes driving). Insome examples, the mobile computing device 100 m may detect when a driveis finished and automatically present the advertisements at that time.

Still, in some embodiments, the user may have the option of viewing theadvertisements. If the user views the advertisements, the user mightavoid getting a ticket for going through the toll without enough fundsto pay for the toll. If the user chooses not to view the advertisements,the user may have to pay the toll and/or a penalty for not having enoughfunds to pay the toll initially.

Returning to step 317, if the mobile computing device 100 m determinesthat the funds were transferred successfully (Yes at step 317), themobile computing device 100 m may output a message indicating that thetoll payment was successful at step 323. Outputting this successfulmessage may include playing an audible tone (e.g., a beeping sound) oraudible message (e.g., a voice recording stating “the toll was paid”).Additionally, or alternatively, the message may include text and/or animage displayed on a screen of the mobile computing device 100 m.Moreover, the message may be communicated by causing the mobilecomputing device 100 m to vibrate. The message at step 323 may bedifferent from the message at step 319 so that users (e.g., drivers) mayeasily discern whether the toll payment was successful or not.

In step 325, advertisements may be played (e.g., displayed) on themobile computing device 100 m. In some embodiments, users may agree toview advertisements in exchange for a discount on the toll payment.Therefore, even in cases where some funds are transferred,advertisements may be presented to a user. The number or type ofadvertisements presented at step 325 may depend on the customer, theamount of the discount, the time that the customer went through thetoll, etc. In some examples, the number of advertisements presented instep 325 may be less than the number of advertisements that would havebeen presented had the toll payment failed.

In some embodiments, the advertisements may automatically be presentedat step 325 shortly after being received. In other embodiments, theadvertisements to be presented at step 325 may be stored locally by themobile computing device 100 m for later presentation to the user (e.g.,after the user finishes driving). In some examples, the mobile computingdevice 100 m may detect when a drive is finished and automaticallypresent the advertisements at that time.

Still, in some embodiments, the user may have the option of viewing theadvertisements. If the user views the advertisements, the user may berefunded a portion of the toll or the previous discount may bevalidated. If the user chooses not to view the advertisements, the usermay have to pay the undiscounted toll amount.

In some embodiments, where advertisements are used, the mobile computingdevice 100 m may determine whether advertisements have been viewed. Auser/customer may not receive the benefits of the advertisements if theadvertisements are not viewed. For example, if the advertisementdisplayed in step 321 or step 325 is a video, the mobile computingdevice 100 m may determine whether the video has been completely playedbefore relieving the customer from having to pay the ticket or beforerewarding the customer with the discount. After steps 321 and 325 arecomplete (assuming advertisements are presented), the process may returnto step 305 at which the mobile computing device 100 m may receiveanother signal for another toll gateway 203 that it passes through.

FIG. 4 illustrates a flow diagram for another example method inaccordance with aspects of the present disclosure. More specifically,FIG. 4 illustrates a plurality of steps of a method for making a tollpayment. The steps of FIG. 4 may be performed by various devicesdisclosed herein, and in particular one or more of the insurance companycomputing devices 205 (e.g., a server of an insurance company). One ormore of the steps of FIG. 4 may be performed by executing a server-sidetoll equipment program and/or operating a particularly configuredcomputing device 100 of the toll payment system. As a result of themethod of FIG. 4, a server of an insurance company may handle payment ofa toll for a customer (e.g., a person with an insurance policy with theinsurance company).

The method of FIG. 4 may begin with a step 401 in which one or more ofthe insurance company computing devices 205 may receive a signal from amobile computing device 100 m or toll gateway 203 indicating that aspecific mobile computing device 100 m passed through a toll gateway203. The signal received in step 401 may include information includingan identifier of the mobile computing device 100 m that was detected, anidentifier of a vehicle 202 in which the mobile computing device 100 mwas located when it passed through the toll gateway 203, a speed of themobile computing device 100 m as it passed through the toll gateway 203,an identifier or location of the toll gateway 203 that the mobilecomputing device 100 m passed through, a time at which the mobilecomputing device 100 m passed through the toll gateway 203, a distancebetween two consecutive vehicles passing through the toll gateway 203(e.g., tailgating information), etc. In some embodiments, the signalreceived in step 401 may correspond to the signal transmitted by themobile computing device 100 m at step 311.

In some embodiments, the signal received in step 401 may indicate theamount owed for the toll. In other embodiments, the signal received instep 401 might not include the amount owed for the toll. In suchembodiments, one or more of the insurance company computing devices 205may determine the amount of the toll due at step 401. This determinationmay be based on time/date information, location information (e.g., GPScoordinates), vehicle information (e.g., number of axels of a vehicle inwhich the mobile computing device is travelling, which may be enteredbased on user responses to a prompt, based on insurance policyinformation, or based on user entered settings), and/or a toll gatewayidentifier included with the signal received at step 401.

In some embodiments, where multiple mobile computing devices 100 m arelocated in the same vehicle 202 and one or more of them are configuredto make toll payments (e.g., are executing a client-side toll equipmentprogram), the insurance company computing device 205 may receivemultiple signals at step 401. The insurance company computing device 205may determine that the signals are from mobile computing devices 100 mwithin the same vehicle 202 based on information in the signals, such asa toll identifier, time of passing through the toll gateway (e.g., timea signal from the toll gateway is received by the mobile computingdevices 100 m), vehicle information, etc. After determining thatmultiple signals have been received for the same vehicle 202, theinsurance company computing device 205 may select one account to becharged the fee for the toll. The selection may be based on userpreferences, insurance related information (e.g., which insurance policyeach user has or what insurance premium a user pays), informationindicating whether a user is eligible for a discount, past toll paymentinformation (e.g., users that have paid less in the past may be selectedto pay the current toll due), etc. or the selection may be random. Inthis manner, the insurance company computing device 205 may prevent avehicle 202 from being over charged for passing through a single tollgateway 203.

Step 403 may include storing the information received in step 401. Theinformation may be stored in a database owned or maintained by aninsurance company or on behalf of the insurance company. The informationmay be stored in association with other information stored by theinsurance company, such as insurance policy information. For example,the insurance company computing device 205 may identify a policy holderbased on an identifier (e.g., telephone number) of the mobile computingdevice 100 m that passed through the toll gateway 203. The insurancecompany computing device 205 may then store the information received instep 401 with other information of the policy holder (e.g., otherinformation on the policy holder's driving behavior).

In step 405, one or more of the insurance company computing devices 205may use the information (or a part thereof) received in step 401 todetermine an insurance related value (e.g., an insurance premium ordeductible) for a policy holder identified in step 403. For example, aninsurance company computing device 205 may use drive data, such as thetailgating information and/or speed information, to determine a drivescore for a customer. The drive score for the customer may be used togauge whether the customer is a safe driver and may be a factor inlowering the customer's insurance premium and/or deductible. On theother hand, an insurance company computing device 205 may use thetailgating information and/or speed information to determine that acustomer is a risky driver so that the customer's insurance premiumand/or deductible is not lowered in the future.

At step 407, one or more of the insurance company computing devices 205may identify a toll account associated with the mobile computing device100 m that was detected passing through the toll gateway 203. The tollaccount may include the funds or keep a record of the funds availablefor a particular policy holder to use for payment of tolls. For example,the toll account may be similar to an online banking account, but may beused exclusively to make toll payments.

Step 409 may include determining whether any discount applies. In somecases, a customer may receive a discount on the toll payment forparticipating in the toll payment system. The amount of the discount maydepend on the customer's insurance policy or a customer's status (whichmay be based on a customer's loyalty or the amount of business thecustomer gives the insurance company). For example, customers who insuremultiple items (e.g., a house and multiple vehicles) with the insurancecompany may receive a greater discount than customers that insure only asingle item with the insurance company. In some cases, the customermight only receive a discount in exchange for sharing information aboutthe customer (e.g., who the customer is driving with when going throughthe toll gateway, when the customer goes through the toll gateway, aspeed of the vehicle 202 as it passes through the toll gateway 203,tailgating information of the vehicle as it passes through the tollgateway 203, etc.). Or, in some cases, the customer may receive adiscount if they agree to receive and/or view advertisements after theypass through toll gateways 203.

In some embodiments, insurance company customers may receive discountson tolls if they agree to carpool. Information collected from the tollgateway 203 and/or mobile computing devices 100 m when a vehicle 202passes through the toll gateway may include information indicating whichmobile computing devices 100 m are within the vehicle 202 (which may beused to represent who is in the vehicle as people have been known tocarry certain mobile computing devices 100 m with them). Thisinformation may be used to determine whether customers are in factcarpooling, and therefore, whether customers are in fact eligible toreceive discounts on tolls or other insurance related values (e.g.,insurance premiums).

In step 411, one or more of the insurance company computing devices 205may transfer funds for the toll payment from the toll account identifiedin step 407. The funds may be transferred to one of the toll managementcomputing devices 204 or an account of the toll company. In someembodiments, the funds may be transferred along with informationindicating the vehicle 202 that passed through the toll gateway 203, anidentifier of the toll gateway 203, and/or a time of passing through thetoll gateway. If there are not enough funds in the identified tollaccount, one or more of the insurance company computing devices 205 maysend a signal to the toll gateway 203 (e.g., the toll gateway computingdevice 209) or one of the toll management computing devices 204indicating the unsuccessful payment. This signal may include informationidentifying the vehicle 202 and/or vehicle owner or operator so that thetoll company may issue a ticket. In some embodiments, this signal maytrigger the camera 211 to take a photograph of a vehicle 202 passingthrough the toll gateway 203 or trigger the camera 211 or toll gatewaycomputing device 209 to store a photograph already taken of the vehicle202 that went through the toll gateway 203 without making the tollpayment.

In step 413, one or more of the insurance company computing devices 205may send a signal to the mobile computing device 100 m. This signal mayinclude information indicating whether the funds were transferredsuccessfully. The signal transferred at step 413 may be similar to thesignal received at step 315 in FIG. 3.

At step 415, one or more of the insurance company computing devices 205may determine which advertisements, if any, to send to the mobilecomputing device 100 m that went through the toll gateway 203. Theadvertisements may be determined based on user preferences orinformation stored in association with an insurance policy. Differentadvertisements may be provided to different mobile computing devices 100m of users depending on the insurance policy of the users. For example,a user with an insurance policy for a luxury vehicle may receivedifferent advertisements than a user with an insurance policy for aneconomy vehicle.

FIG. 5 illustrates a flow diagram for an example method in accordancewith aspects of the present disclosure. More specifically, FIG. 5illustrates a plurality of steps of a method for making a toll payment.The steps of FIG. 5 may be performed by various devices disclosedherein, and in particular one or more devices of the toll gateway (e.g.,the toll gateway computing device 209). One or more of the steps of FIG.3 may be performed by executing a gateway-side toll equipment programand/or operating a particularly configured computing device 100 of thetoll payment system. As a result of the method of FIG. 5, a toll gateway203 may allow a vehicle 202 to pass without issuing a ticket if phone inthe vehicle is used to make a toll payment.

The method of FIG. 5 may begin with a step 501 in which beacon signal istransmitted. In step 503, the toll gateway 203 may receive a responsesignal from a mobile computing device 100 m. After receiving theresponse signal, the toll gateway 203 may identify the mobile computingdevice 100 m in step 505. At step 507, the toll gateway 203 maydetermine whether the toll payment was made for a vehicle 202 carryingthe mobile computing device 100 m. If the toll payment was not made, thetoll gateway 203 may instruct the camera 211 to take a photograph of thevehicle 202 in step 509. If a photograph of the vehicle 202 waspreviously taken, then the photograph may be obtained in step 509. Afterobtaining the photograph, the toll gateway 203 may determine whether toissue a ticket or citation at step 511. If the vehicle 202 that passedthrough the toll gateway 203 without paying the toll belongs to acustomer of the insurance company, a ticket might not be issued. Forexample, the insurance company may cover the toll for the customer atstep 513 and add a fee to the customer's insurance premium for the nextpayment cycle (e.g., monthly payment). Step 513 may include searching acustomer database of an insurance company. If the vehicle 202 does notbelong to a customer of the insurance company (or if the vehicle 202 isnot insured by the insurance company), the toll gateway may issue aticket or citation in step 515. After steps 507, 513, and 515, the tollgateway 203 may report collected data to one or more of the insurancecomputing devices 205 in step 517. For example, the toll gateway 203 maysend information, such as speed data or tailgating data of a vehicle 202going through the toll gateway, to the insurance company. The insurancecompany may use this information in evaluating the risk of customers andpotential customers in order to determine insurance rates (e.g.,insurance premiums). At step 517, the toll gateway 203 may also send, tothe insurance company, information indicating a time and location of thepayment and information indicating other mobile computing devices 100within the vehicle 202.

FIG. 6 illustrates a flow diagram for an example method in accordancewith aspects of the present disclosure. More specifically, FIG. 6illustrates a plurality of steps of a method for determining which of aplurality of mobile computing devices 100 m within a vehicle 202 isresponsible for handling a toll payment. The steps of FIG. 6 may beperformed by various devices disclosed herein, and in particular mobilecomputing devices 100 m, such as cell phones within the vehicle 202. Oneor more of the steps of FIG. 6 may be performed by executing aclient-side toll equipment program and/or operating a particularlyconfigured computing device 100 of the toll payment system. As a resultof the method of FIG. 6, the phones in a vehicle 202 may discover oneanother and select a dominant phone to take responsibility for paying atoll.

The method of FIG. 6 may begin with a step 601 in which one or moremobile computing devices 100 m within a vehicle 202 send a signal todiscover the other mobile computing devices 100 m within the vehicle202. For example, a first phone in the vehicle 202 may transmit (orbroadcast) a signal that may be picked up by a second phone in thevehicle 202. This transmitted signal may be sent using a local wirelessprotocol, such as ZigBee or Bluetooth.

In step 603, the mobile computing device 100 m that transmitted thesignal in step 601 may receive a response signal from another mobilecomputing device 100 m within the vehicle (assuming there is one).

In step 605, the mobile computing device 100 m that transmitted thesignal in step 601 may determine whether there is another mobilecomputing device 100 m within the same vehicle 202. If a set amount oftime has passed since the signal was transmitted in step 601 and noresponse is received, the mobile computing device 100 m may determinethat there is no other mobile computing device 100 m within the vehicle202. If a response signal is received at step 603, the mobile computingdevice 100 m may determine whether the response signal is from anothermobile computing device 100 m within the vehicle 202 that is configuredto make toll payments (e.g., is running a client-side toll equipmentprogram).

If no other mobile computing device 100 m configured to make tollpayments is detected (No at step 605), the mobile computing device 100 mperforming step 601 may undergo a delay at step 607. For example, themobile computing device 100 m that performed step 601 may wait for apredetermined time before performing step 601 again.

On the other hand, if it is determined that another mobile computingdevice 100 m is in the vehicle 202 and configured to make toll payments,the mobile computing devices 100 m may determine which mobile computingdevice 100 m should take responsibility for making toll payments (e.g.,should be the dominant mobile computing device 100 m) at step 609. Thisdetermination may include exchanging communications between the mobilecomputing devices 100 m to determine user preferences associated witheach of the mobile computing devices 100 m. For example, a mother'sphone may communicate with a daughter's phone to determine themother-daughter relationship and select the mother's phone to be thedominant phone. Users may set an order for this determination within thesettings of a client-side toll equipment program. For example, a mothermay control settings so that her husband's phone should be used insteadof her phone to make toll payments, but her phone should be used insteadof her son's phone and daughter's phone. If settings do not dictatewhich phone is to be the dominant phone, one of the phones may berandomly selected as the dominant phone.

Additionally, or alternatively, the determination of which mobilecomputing device 100 m is to be the dominant mobile computing device 100m may be based on a location of the mobile computing devices 100 mwithin the vehicle 202. The location of the mobile computing devices 100m within the vehicle may be determined based on GPS coordinates orcommunications with the vehicle computing device or an OBD device 207.For example, a phone that is closest to an OBD device 207 connected tothe OBD II port in the vehicle 202 (which is typically on the driver'sside below the steering wheel) may be set as the dominant phone in step609. Step 609 may also include informing each of the discovered mobilecomputing devices 100 m whether or not they are the dominant mobilecomputing device 100 m. For example, the mother's phone may inform theson's phone that his phone is not the dominant phone.

FIG. 7 provides a diagram illustrating an example sequence of signals inaccordance with aspects of the present disclosure. The sequence ofsignals may begin when signal 1 is transmitted. As shown in FIG. 7,signal 1 may be transmitted from a toll gateway 203 to a mobilecomputing device 100 m (e.g., a phone). Signal 1 may be transmitted inresponse to detecting an approaching vehicle. Or, the toll gateway 203may be configured to transmit the signal 1 regardless of whether avehicle is approaching. For example, the signal 1 may be transmittedcontinuously or intermittently (e.g., at periodic intervals). The signal1 may be a beacon signal intended for receipt by a phone traveling in avehicle 202 passing through the toll gateway 203.

In response to the signal 1, the phone may send a signal 2 back to thetoll gateway 203. Signal 2 may indicate that the phone is passingthrough the toll gateway 203. Signal 2 may indicate that the phone hasreceived signal 1 and will handle paying the toll. Signal 2 may includean identifier identifying the phone or vehicle.

In response to the signal 1, the phone may also send a signal 3 to theinsurance company computing device 205. Signal 3 may include informationidentifying the toll gateway 203 and/or a location of the phone.

In response to signal 3, the insurance company computing device 205 maysend a signal 4 to transfer funds to the toll management computingdevice 204. The amount of the funds transferred may be equal to the tollrequired or may be less if any discount is applicable.

In response to signal 3, the insurance company computing device 205 maysend a signal 5 to inform the phone that the toll payment was made.Signal 5 may cause the phone to alert the driver that the toll paymentwas made (e.g., to play an audible tone).

In response to signal 4, the toll management computing device 204 maysend signal 6 to inform the toll gateway 203 that funds were received topay the toll for the vehicle that was carrying the phone that sentsignal 2. Signal 6 may include an identifier indicating a phone and/orvehicle that passed through the toll gateway 203 and/or a time that thevehicle/phone passed through the toll gateway 203.

In response to signal 6 or signal 2, the toll gateway 203 may sendsignal 7 to provide the insurance company computing device 205 withdriving information collected for the vehicle 202 that passed throughthe toll gateway 203. This driving information may include a speed ofthe vehicle as it passed through the toll gateway 203 and/or whether thevehicle was tailgating another vehicle or being tailgated. In someembodiments, the distance of the tailgating may be included in signal 7.

It should be understood that the signals in FIG. 7 may each include oneor more signals. For example, signal 7 may include one signal to sendspeed information and another signal to send tailgating information.Also, each signal may include one or more packets (e.g., IPv4 or IPv6packets) of data. Further, the order of the signals may be different inother embodiments. For example, signal 3 may be sent before signal 2.Also, signals are described as being in response to other signals,however, other events or signals may trigger the transfer of thesignals. For example, signal 6 may be sent in response to a request fromthe toll gateway 203 to the toll management computing device 204 forinformation indicating whether a toll has been paid for a particular thevehicle 202.

FIG. 8 illustrates an example interface 800 in accordance with aspectsof the present disclosure. This interface may be displayed on a screenof a mobile computing device 100 m (e.g., a smartphone) after it haspassed through a toll gateway. In some embodiments, the interface ofFIG. 8 may be displayed on a screen of a mobile computing device 100 msoon after (e.g., within 5 minutes) the mobile computing device 100 mpasses through a toll gateway 203. It should be understood that the userinterface 800 of FIG. 8 is intended to illustrate various features andaspects of the toll payment system, and that interfaces are not limitedto the visual appearance or layout depicted in FIG. 8.

As shown in FIG. 8, the interface 800 may include a message to a user(e.g., driver or passenger) of the mobile computing device 100 mindicating that a toll payment was successfully completed (e.g., fundswere transferred). The message may include the amount paid and adescription of the toll (e.g., an indicator of the toll road). Themessage may also indicate whether any discounts were applied. Further,interface 800 may display information about the vehicle 202 that themobile computing device 100 m is traveling in when it passed through thetoll. The interface 800 may also include a link to other driving datacollected at the toll gateway 203, such as speed data and tailgatingdata.

Interface 800 may also indicate an account balance of the toll accountfrom which funds are transferred to make toll payments. This may allow auser to readily view their account balance and add funds if necessary ordesired. Interface 800 may also include options for viewing past tollinformation, such as what other tolls the user has passed through andhow much money a user has spent on tolls. In addition, the interface 800may include an option for users to view advertisements. As explainedabove, users may receive advertisements in exchange for reduced tollrates or failing to pay tolls.

The interface 800 may also include an option to change settings. Forexample, the user may change settings used to determine which mobilecomputing device 100 m is to be the dominant mobile computing device 100m when multiple mobile computing devices 100 m are within the samevehicle.

Aspects of the invention have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one of ordinary skill in the art willappreciate that the steps shown in the illustrative figures may beperformed in other than the recited order, and that one or more stepsillustrated may be optional in accordance with aspects of the invention.For example, referring to FIG. 5, the order of steps 501 and 503 may beswapped so that the mobile computing device 100 m transmits a signal tothe toll gateway 203 first and receives a response from the toll gateway203.

What is claimed is:
 1. A system, comprising: a first computing deviceassociated with a first vehicle, wherein the first computing device isconfigured to send and receive cellular phone calls; a toll gatewayconfigured to: detect the first vehicle if the first vehicle passesthrough the toll gateway; and communicate with the first computingdevice; and an insurance company computing device configured to:transfer funds from an account associated with the first computingdevice in response to receiving, from the first computing device or thetoll gateway, a signal indicating that the first vehicle passed throughthe toll gateway; receive, from the first computing device or the tollgateway, drive data of the first vehicle while the first vehicle passedthrough the toll gateway; and determine an insurance related value basedon the drive data.
 2. The system of claim 1, wherein the first computingdevice comprises a cell phone of a driver of the first vehicle and islocated within the first vehicle.
 3. The system of claim 1, wherein thetoll gateway is configured to transmit a beacon signal to detect thefirst computing device, and wherein the first computing device isconfigured to receive the beacon signal and transmit a response signalto the toll gateway in response to receiving the beacon signal.
 4. Thesystem of claim 3, wherein the beacon signal comprises an identifieridentifying the toll gateway, and wherein the response signal comprisesan identifier identifying the first computing device.
 5. The system ofclaim 3, wherein the first computing device executes a program that runsin a background of the first computing device to detect the beaconsignal.
 6. The system of claim 1, wherein the first computing device isfurther configured to: determine whether a toll payment is owed; and inresponse to determining that a toll payment is owed, transmit, to theinsurance company computing device, information identifying the firstcomputing device and information identifying the toll gateway that thefirst vehicle passed.
 7. The system of claim 1, wherein the firstcomputing device is further configured to transmit, to the toll gateway,a signal indicating that a toll payment was made or will be made.
 8. Thesystem of claim 1, wherein the first computing device is furtherconfigured to provide a user with a message indicating that a tollpayment was successfully completed.
 9. The system of claim 8, whereinthe message comprises an audible tone.
 10. The system of claim 1,wherein the toll gateway comprises a camera configured to take aphotograph of the first vehicle.
 11. The system of claim 1, wherein theinsurance company computing device is further configured to: determinewhether a toll payment is successful; select one or more advertisementsbased on whether the toll payment is successful; and transmit the one ormore advertisements to the first computing device.
 12. The system ofclaim 1, wherein the insurance company computing device is furtherconfigured to: determine an amount of a toll due as a result of thefirst vehicle passing through the toll gateway; identify the accountassociated with the first computing device; determine whether anydiscount to the toll applies for the first computing device; anddetermine whether there are sufficient funds in the account to cover thetoll.
 13. The system of claim 12, wherein the insurance companycomputing device is further configured to: transmit an advertisement tothe first computing device in response to determining that the funds inthe account are insufficient to cover the toll; or transfer funds froman account of an insurance company to cover the toll.
 14. The system ofclaim 1, wherein the drive data comprises a speed of the first vehicleas it passed through the toll gateway or tailgating informationindicating whether the first vehicle was tailgating while passingthrough the toll gateway.
 15. The system of claim 14, wherein thetailgating information comprises a distance between the first vehicleand a second vehicle passing through the toll gateway immediately aheadof the first vehicle.
 16. The system of claim 1, wherein the insurancerelated value comprises at least one of an insurance premium, aninsurance deductible, or a drive score used in determining the insurancepremium or the insurance deductible.
 17. A computing device, comprising:a network interface configured to communicate, via a network, with amobile computing device and a toll gateway, wherein the mobile computingdevice is configured for use in cellular phone calls and wherein thetoll gateway is configured to detect a vehicle if the vehicle passesthrough the toll gateway; and at least one processor configured to:receive, from the mobile computing device or the toll gateway via thenetwork interface, a signal indicating that the vehicle passed throughthe toll gateway; in response to receiving the signal, transmit anelectronic payment for a toll associated with the toll gateway; receive,from the mobile computing device or the toll gateway via the networkinterface, drive data of the vehicle while the vehicle passed throughthe toll gateway; and determine an insurance related value based on thedrive data.
 18. The computing device of claim 17, wherein the at leastone processor is further configured to: determine an amount of the toll;identify an account associated with the mobile computing device;determine whether any discount to the toll applies for the mobilecomputing device; and determine whether there are sufficient funds inthe account to cover the toll.
 19. A method, comprising receiving, by amobile computing device configured for use in cellular phone calls, abeacon signal as the mobile computing device within a vehicle passesthrough a toll gateway; transmitting, to an insurance company computingdevice via a cellular backhaul, a signal indicating that the vehicle haspassed through the toll gateway; in response to receiving the signal,determining an account associated with the mobile computing device;transferring funds from the account to pay a toll associated with thetoll gateway; receiving, from the mobile computing device or the tollgateway, drive data of the vehicle while the vehicle passed through thetoll gateway; and determining an insurance related value based on thedrive data.
 20. The method of claim 19, further comprising determiningwhether any discount on the toll is applicable prior to transferring thefunds; and sending a signal to the mobile computing device indicatingthat the toll was paid and whether any discount was applied.